Providing real-time sensor based information via an augmented reality application

ABSTRACT

A device may receive, from a user device, information that identifies a geolocation of the user device. The device may determine a set of sensor devices that are associated with the geolocation. The device may request, from the set of sensor devices, real-time information associated with the geolocation based on determining the set of sensor devices. The device may receive, from the set of sensor devices, the real-time information associated with the geolocation based on requesting the real-time information. The device may provide, to the user device, the real-time information associated with the geolocation to permit the user device to provide, for display, the real-time information as an augmented reality overlay.

BACKGROUND

Augmented reality (AR) applications enable a user, utilizing a userdevice, to view a real-world environment that is augmented bycomputer-generated content, such as images, video, text, or the like.For example, the user device may provide, for display, a view ofreal-world surroundings of the user that may include superimposedcontent.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1T are diagrams of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2;

FIG. 4 is a flow chart of an example process for providing real-timesensor based information via an augmented reality application;

FIG. 5 is a flow chart of an example process for providing informationto an entity server based on crowdsourced information associated with ageolocation; and

FIGS. 6A-6E are diagrams of an example implementation relating to theexample process shown in FIG. 5.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A user, such as an inhabitant or a visitor of a particular geolocation,may wish to ascertain information regarding the geolocation (e.g., atown, a city, or the like). For example, the user may wish to ascertainhistorical, current, and/or upcoming information associated with thegeolocation as the user navigates throughout the geolocation (e.g., tobecome more familiar with the geolocation, to identify activitiesassociated with the geolocation, etc.). Additionally, the user may wishto provide information to other users associated with the geolocationand/or users associated with an entity associated with the geolocation(e.g., a government agency, an emergency response department, anorganization, a business, or the like). For example, the user may wishto initiate discourse regarding the geolocation (e.g., between othercitizens of the geolocation and/or users associated with an entity),opine on an issue associated with the geolocation, or the like.Implementations described herein enable a user device, via an augmentedreality (AR) application, to provide information for display that mayenable the user to learn about and/or contribute to a communityassociated with the geolocation.

Implementations described herein enable a server device to aggregateinformation associated with a geolocation using information frommultiple disparate data sources (e.g., external server devices, sensordevices associated with the Internet of things (IoT), user devices,etc.), and provide the information to a user device such as asmartphone, a headset such as an AR/virtual reality (VR) visor, userglasses, a tablet, or other devices. The user device may provide, fordisplay via a user interface and an AR application, the informationassociated with the geolocation including AR overlays. In this way, theuser may view real-time information as the user navigates thegeolocation, interact with the user device to generate user generatedcontent that may be viewed by other users, report feedback to an entityassociated with the geolocation, and/or the like. Additionally, in thisway, implementations described herein enable relevant content to beprovided to the user device, thereby reducing a need of the user deviceto perform searches for particular information. For example,implementations described herein may reduce an amount of instances wherethe user causes the user device to perform a search for particularinformation, such as information associated with the geolocation, eventsof the geolocation, etc. In this way, implementations described hereinconserve processor and/or memory resources of the user device and/orconserve network resources by reducing an amount of searches performedby the user device.

FIGS. 1A-1T are diagrams of an overview of an example implementation 100described herein. As shown in FIG. 1A, a user device may provideinformation, for display, based on executing an application (e.g., acitizen engagement application). For example, the application mayinclude a geolocation based AR application for discovering and/orreporting information associated with a geolocation. As shown, the userdevice may provide, for display, information associated with multiplemissions based on a geolocation of the user device. A mission mayinclude a curated and/or geolocation based user experience that involvesaugmented reality, IoT data, and/or other accessible data associatedwith a geolocation. As an example, a mission may include a set ofactions to be performed by a user of the user device in association witha geolocation. In some implementations, an engagement platform (e.g., acloud server device) may provide, to the user device, informationassociated with particular missions based on a geolocation of the userdevice. As examples, a “history” mission may encourage the user todiscover historical information associated with the geolocation, a“current” mission may encourage the user to discover current eventsand/or conversations associated with the geolocation, and an “impact”mission may encourage the user to provide input and/or feedbackregarding the geolocation.

In some implementations, the engagement platform may provide, to theuser device, information associated with particular missions based oninformation associated with the user (e.g., curated missions based onuser preferences, completed missions, friend activity, etc.).Additionally, or alternatively, the engagement platform may provide, tothe user device, information associated with particular missions basedon popularities of the missions determined, for example, by an amount ofusers that have completed the missions, rankings of the missionsdetermined by user feedback, particular entities associated with themissions, or the like.

As shown in FIG. 1B, the user device may provide, for display, a mapview of the geolocation that includes user interface elements thatidentify particular missions. Additionally, as shown, the user devicemay provide, for display, a current location of the user. As shown byreference number 102, assume that the user interacts (e.g., performs atouch gesture, such as a tap) with a user interface element associatedwith a menu.

As shown in FIG. 1C, the user device may provide, for display, a menuthat enables the user to select particular missions and/or informationto be provided for display. As shown by reference numbers 104, 106, and108 respectively, assume that the user selects “history” missions,“impact” missions, and “user pins” information to be provided fordisplay.

As shown in FIG. 1D, the user device may provide, for display, the mapview of the location that includes user interface elements thatcorrespond to the selected missions and/or information, and includes thecurrent location of the user. As shown by reference number 110, assumethat the user interacts with a particular user interface elementassociated with a particular “history” mission.

As shown in FIG. 1E, the user device may provide, for display, the mapview that includes a route associated with the selected mission and thecurrent location of the user. Additionally, as shown, the user devicemay prevent information associated with other missions from beingprovided for display based on the user selection of the particularmission. As shown by reference number 112, assume that the userinteracts with a user interface element associated with an AR view.

As shown in FIG. 1F, the user device may provide, for display, an ARview associated with surroundings of the user device. For example, asshown, the user device may provide, for display, imagery captured by acamera of the user device and superimposed AR overlays. In someimplementations, the user device may include functionality fordetermining geolocation information. For example, geolocationinformation may include information that identifies a geographiclocation (e.g., geographic coordinates, or the like) and/or anorientation (e.g., a horizontal and/or vertical orientation, or thelike) of the user device. In some implementations, the user device mayutilize global positioning system (GPS) information, compassinformation, and/or accelerometer information to determine thegeolocation information. In some implementations, the user device mayprovide, for display, the superimposed AR overlays based on geolocationinformation of the user device. That is, the user device may superimposea particular AR overlay, that corresponds to a real-world surrounding(e.g., a building, a venue, etc.), in association with the real-worldsurrounding based on geolocation information.

As shown in FIG. 1G, the user device may provide, for display, an ARoverlay associated with the selected mission. For example, assume thatthe user directs the user device towards a particular building. Asshown, the AR overlay may be superimposed in association with thebuilding. For example, the AR application may cause imagery data,associated with a camera of the user device, to be superimposed with theAR overlay based on geolocation information of the user device (e.g.,that indicates that the user device is directed towards the building).As shown, the user device may provide, for display, information thatidentifies a direction and/or a distance to a starting point of themission. As an example, assume that the starting point of the missionincludes a kiosk device (e.g., a smart kiosk device that includeswireless local area network (WLAN) connectivity). Additionally, assumethat the user navigates to the kiosk device. In some implementations, astarting point of a mission may include a destination point of anothermission, a centralized geolocation of a set of missions, a particulargeolocation associated with an entity (e.g., a featured starting pointor destination), or the like.

As shown in FIG. 1H, the user device may utilize a quick response (QR)code scanner to interact with the kiosk device. As an example, the usermay direct the user device towards the kiosk device to scan a QR codethat is being provided for display via the kiosk device. In someimplementations, the kiosk device may provide, to the user device via aWLAN connection, information associated with a mission based on the userdevice scanning the QR code. As an example, in this case, the kioskdevice may provide, to the user device, information associated with theselected mission (e.g., background information associated with thebuilding). In some implementations, the kiosk device may provide theinformation associated with the mission. Additionally, or alternatively,the kiosk device may provide connectivity between the user device andthe engagement platform, and the user device may receive the informationfrom the engagement platform (or another server device).

As shown in FIG. 1I, the user device may provide, for display,information associated with the selected mission. For example, the userdevice may provide, for display, imagery captured by the user device andAR overlays associated with the selected mission. For example, as shown,particular AR overlays may correspond to particular buildings that arebeing provided for display via the user interface of the user device. Asshown by reference number 114, assume that the user interacts with aparticular AR overlay.

As shown in FIG. 1J, the user device may provide, for display,information associated with the selected AR overlay. For example, theselected AR overlay corresponds to a particular building. In this case,the user device may provide, for display, content associated with theparticular building, such as images, text, audio, etc. For example, theinformation associated with the mission may include content, such asbackground information of the building, historical image informationassociated with the building, or the like. The user may interact withthe user device to scroll through the content, which may cause the userdevice to update a display of the content. Assume that the user scrollsthrough the entirety of the content.

As shown in FIG. 1K, the user device may provide, for display, imagerycaptured by the user device and updated AR overlays associated with theselected mission. For example, the user device may update an AR overlayassociated with the building, thereby indicating that the user completeda portion of the mission corresponding to the building. As shown byreference number 116, assume that the user interacts with another ARoverlay associated with another building. In this case, the user devicemay provide, for display, information associated with the other buildingin a similar manner as described above in connection with FIG. 1J.Assume that the user completes the portion of the mission associatedwith the other building.

As shown in FIG. 1L, the user device may provide, for display, updatedimagery and an updated AR overlay based on the user adjusting anorientation of the user device. As shown by reference number 118, assumethat the user interacts with the AR overlay, and completes the portionof the mission in a similar manner as described above.

As shown in FIG. 1M, the user device may provide, for display,information that identifies that the user has completed the selectedmission. As shown, the user device may provide, for display, informationthat identifies a “level” associated with the user. For example, theapplication may include a user profile associated with the user (e.g.,information that identifies a name, a picture, a set of interests, etc.associated with the user). In some implementations, the user may beassociated with a particular level (e.g., a rank, a designation, or thelike) based on an amount of completed missions. Additionally, oralternatively, a user may obtain points, rewards, etc. based oncompleting missions, based on generating user generated content, basedon interacting with other users and/or entities, etc.

As shown in FIG. 1N, the user device may provide, for display, a mapview of the location that includes additional missions. As shown byreference number 120, assume that the user interacts with a “current”mission (e.g., “Food Fest”). In some implementations, a current missionmay include a mission that involves a live and/or approaching event,such as a food fair, a parade, a concert, a performance, or the like.For example, users associated with particular entities (e.g., localbusinesses, local organizations, etc.) may create sponsored missionsthat involve the particular entities.

As shown in FIG. 1O, the user device may provide, for display,information associated with the selected mission. For example, as shown,the user device may provide, for display, content that identifiesinformation associated with the event. As an example, the informationassociated with the selected mission may include a time of the event, alocation of the event, a hyperlink that may provide access to a resourceassociated with the event, a list of people that have signed up for theevent, comments associated with the event, or the like.

As shown in FIG. 1P, the user device may provide, for display,information based on real-time information associated with sensordevices. For example, the engagement platform may receive, from sensordevices (e.g., IoT sensors, such as traffic cameras, kiosk devicecameras, environmental sensors, sensors associated with other userdevices, sensors associated with unmanned aerial vehicles (UAVs), or thelike), information associated with a geolocation (e.g., that identifiesan increase in traffic associated with the geolocation, an increase inan amount of people associated with the geolocation, safety issuesassociated with the geolocation, or the like). Additionally, theengagement platform may provide, to the user device and based on ageolocation of the user device, the real-time information associatedwith the sensor devices. For example, as shown, the user device mayprovide, for display, information that identifies that trafficcongestion is likely based on traffic analysis.

As shown in FIG. 1Q, the user device may provide, for display,information that enables a user to generate content associated with thegeolocation. For example, a user may interact with the user device togenerate content (e.g., user generated content, such as an image, text,video, etc.) in association with the geolocation, which may cause theuser device to provide, to the engagement platform, information thatidentifies the user generated content. Additionally, other user devicesmay receive and provide, for display, information that identifies theuser generated content. In this way, a user may contribute a thought,provide an opinion, report an issue, solicit feedback, or the like, inassociation with the geolocation. As an example, assume that the userlocates a particular issue associated with the geolocation (e.g., atrash receptacle has exceeded capacity), and wishes to report the issueto an entity that is responsible for handling the issue and/or wishes tonotify other users of the issue.

As shown in FIG. 1R, the user may interact with the user device tocapture an image associated with the trash receptacle. As shown in FIG.1S, the user may interact with the user device to input text, audio,video, etc., in association with the image, and as shown by referencenumber 122, may interact with the user device to provide an alert. Forexample, an alert may include information that may be provided to anentity server device associated with an entity (e.g., a governmentagency, or the like).

As shown in FIG. 1T, another user device (e.g., associated with anotheruser) may provide, for display, information associated with the usergenerated content. For example, based on geolocation information of theother user device, the other user device may receive, from theengagement platform, information that identifies the user generatedcontent and provide the information that identifies the user generatedcontent for display. In this way, the other user may interact with theuser generated content (e.g., may up-vote, down-vote, flag, comment,etc.), which may cause the other user device to provide responseinformation to the engagement platform (e.g., information that isresponsive to and/or involves the user generated content). Additionally,in this way, the engagement platform may provide, to the entity serverdevice, information that identifies the user generated content (e.g.,the alert) and the response information. In this way, users that areassociated with a geolocation may identify an issue and cause respectiveuser devices to provide information that identifies the issue to theengagement platform and/or the entity server device. Additionally, inthis way, an entity that is responsible for performing a particularaction in association with the geolocation may identify the informationassociated with the issue, and take corrective action.

In this way, implementations described herein enable a user device toprovide an AR application that enables a user to ascertain informationassociated with a location, report issues associated with a location,foster discourse in the community associated with a location, or thelike. Additionally, implementations described herein enable anengagement platform to provide, to a user device, information that isassociated with a geolocation (e.g., pertinent information thatidentifies historical information, current events, ongoingconversations, safety issues, etc.). In this way, the user device mayreceive and provide, for display, the information, thereby enabling auser to readily ascertain the pertinent information. In this way,implementations described herein reduce an amount of searches (e.g.,initiated by a user) for information associated with a geolocation,thereby conserving processor, memory, and/or network resources (e.g.,based on providing pertinent information). Additionally, implementationsdescribed herein enable the engagement platform to receive, from sensordevices and/or user devices, real-time information (e.g., real-timesensor information which is output from a sensor substantiallyconcurrently with the sensor detecting the information) associated witha geolocation. Additionally, implementations described herein enable theengagement platform to provide, to a user device, the real-timeinformation. The user device may provide, for display, the real-timeinformation as one or more AR overlays.

As indicated above, FIGS. 1A-1T are provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIGS. 1A-1T.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include a user device 210, an engagement platform220, a sensor device 230, an entity server device 240, an externalserver device 250, a kiosk device 260, and a network 270. Devices ofenvironment 200 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

User device 210 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith real-time information associated with a geolocation. For example,user device 210 may include a communication and/or computing device,such as a mobile phone (e.g., a smart phone, a radiotelephone, etc.), alaptop computer, a tablet computer, a handheld computer, a gamingdevice, a wearable communication device (e.g., a smart wristwatch, apair of smart eyeglasses, an AR and/or VR headset device, etc.), or asimilar type of device.

Engagement platform 220 includes one or more devices capable ofreceiving, processing, storing, and/or providing real-time informationassociated with a geolocation. For example, engagement platform 220 mayinclude a computing device, such as a server (e.g., an applicationserver, a cloud server, a host server, a web server, a hypertexttransfer protocol (HTTP) server, etc.), a network device, or a similardevice. In some implementations, engagement platform 220 may provide anapplication programming interface (API), and/or may request and/orreceive information, from user device 210, sensor device 230, entityserver device 240, and/or external server device 250 via one or moreAPIs.

In some implementations, engagement platform 220 may be hosted in acloud computing environment. For example, the cloud computingenvironment may include a group of computing resources, such asapplications, virtual machines, virtualized storage, hypervisors, or thelike. In some implementations, the cloud computing environment mayprovide computation, software, data access, storage, etc. services thatdo not require end-user (e.g., user device 210) knowledge of a physicallocation and configuration of system(s) and/or device(s) that hostsengagement platform 220. In some implementations, engagement platform220 may not be cloud-based (i.e., may be implemented outside of a cloudcomputing environment) or may be partially cloud-based.

Sensor device 230 includes one or more devices capable of receiving,processing, storing, and/or providing real-time information associatedwith a geolocation. In some implementations, sensor device 230 includesone or more machine-to-machine (M2M) devices and/or one or more IoTdevices. For example, sensor device 230 may include a camera (e.g., atraffic camera, a security camera, a camera associated with a UAV,etc.), an environmental sensor (e.g., a temperature sensor, a lightsensor, an air quality sensor, a smoke sensor, a pressure sensor, anoise sensor, etc.), a vehicle sensor, a traffic sensor, a biometricdevice, a security device, and/or a similar type of device. In otherwords, sensor device 230 may be any “thing” in the IoT. While FIG. 2shows a single sensor device 230, in practice, there may be hundreds,thousands, or millions of sensor devices 230 detecting various kinds ofsensor data.

Entity server device 240 includes one or more devices capable ofreceiving, storing, processing, and/or providing information associatedwith an entity. For example, entity server device 240 may include acomputing device, such as a server device or a similar device. In someimplementations, entity server device 240 may provide, to a clientdevice (e.g., a desktop computer, a smart phone, or the like), adashboard (e.g., user interface) that enables a user (e.g., a personaffiliated with the entity, such as a government official, or the like)to view information associated with a geolocation, provide informationin association with the geolocation, or the like.

External server device 250 includes one or more devices capable ofreceiving, storing, processing, and/or providing information associatedwith a geolocation. For example, external server device 250 may includea computing device, such as a server device or a similar device. In someimplementations, external server device 250 may provide information,such as historical information, current information, backgroundinformation, etc. associated with a geolocation.

Kiosk device 260 includes one or more devices capable of receiving,storing, processing, and/or providing information associated with ageolocation. For example, kiosk device 260 may include a computingdevice that may provide WLAN connectivity to user device 210. Forexample, kiosk device 260 may interface with user device 210 via a QRcode, a near-field communication (NFC), a radio-frequency identification(RFID), Bluetooth, a WLAN, and/or the like, and may provide informationto user device 210, and/or provide connectivity to network 270. In someimplementations, kiosk device 260 may provide, for display, informationassociated with a geolocation (e.g., weather information, transitinformation, public information, hyper-local advertisement information,etc.).

Network 270 includes one or more wired and/or wireless networks. Forexample, network 270 may include a cellular network (e.g., a long-termevolution (LTE) network, a third generation (3G) network, a codedivision multiple access (CDMA) network, etc.), a public land mobilenetwork (PLMN), a local area network (LAN), a wide area network (WAN), ametropolitan area network (MAN), a telephone network (e.g., the PublicSwitched Telephone Network (PSTN)), a private network, an ad hocnetwork, an intranet, the Internet, a fiber optic-based network, a cloudcomputing network, or the like, and/or a combination of these or othertypes of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to user device 210, engagement platform 220, sensordevice 230, entity server device 240, external server device 250, and/orkiosk device 260. In some implementations, user device 210, engagementplatform 220, sensor device 230, entity server device 240, externalserver device 250, and/or kiosk device 260 may include one or moredevices 300 and/or one or more components of device 300. As shown inFIG. 3, device 300 may include a bus 310, a processor 320, a memory 330,a storage component 340, an input component 350, an output component360, and a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320includes a central processing unit (CPU), a graphics processing unit(GPU), an accelerated processing unit (APU), a microprocessor, amicrocontroller, a digital signal processor, a field-programmable gatearray (FPGA), an application-specific integrated circuit (ASIC), oranother type of processing component. In some implementations, processor320 includes one or more processors capable of being programmed toperform a function. Memory 330 includes a random access memory (RAM), aread only memory (ROM), and/or another type of dynamic or static storagedevice (e.g., a flash memory, a magnetic memory, and/or an opticalmemory) that stores information and/or instructions for use by processor320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, a compass, and/oran actuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes in response to processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for providing real-timesensor based information via an augmented reality application. In someimplementations, one or more process blocks of FIG. 4 may be performedby user device 210 and/or engagement platform 220. In someimplementations, one or more process blocks of FIG. 4 may be performedby another device or a group of devices separate from or including userdevice 210 and/or engagement platform 220 such as sensor device 230,entity server device 240, external server device 250, and/or kioskdevice 260.

As shown in FIG. 4, process 400 may include providing, to a serverdevice, geolocation information associated with a user device (block410). For example, user device 210 may provide, to engagement platform220, geolocation information that identifies a geographic locationand/or an orientation of user device 210. In some implementations, userdevice 210 may include functionality for determining geolocationinformation of user device 210. For example, user device 210 may utilizeGPS information, compass information, accelerometer information, signaltriangulation, and/or the like to determine geolocation informationand/or an orientation of user device 210. Additionally, oralternatively, user device 210 may establish a connection (e.g., a WLANconnection, an NFC connection, etc.) with kiosk device 260, and providethe geolocation information based on establishing the connection.

As further shown in FIG. 4, process 400 may include receiving thegeolocation information and requesting, from a set of sensor devices,real-time information associated with the geolocation (block 420). Forexample, engagement platform 220 may receive, from user device 210, thegeolocation information, determine a set of sensor devices 230associated with the geolocation, and request real-time informationassociated with the geolocation from the set of sensor devices 230.

In some implementations, engagement platform 220 may determine a set ofsensor devices 230 associated with the geolocation based on informationstored in a data structure, based on information received from anotherdevice (e.g., sensor device 230, entity server device 240, etc.), or thelike. In some implementations, engagement platform 220 may identifyparticular types of sensor devices 230 based on the set of sensordevices 230, and identify particular communication protocols forcommunicating with sensor devices 230. For example, the set of sensordevices 230 may include different types of sensor devices 230 (e.g.,traffic cameras, cameras associated with UAVs, temperature sensors,etc.) that may implement different communication protocols and/orprovide information associated with different data formats, etc.

In some implementations, engagement platform 220 may request thereal-time information from each sensor device 230 of the set of sensordevices 230. Alternatively, engagement platform 220 may request thereal-time information from a subset of sensor devices 230. In someimplementations, engagement platform 220 may identify multiple sensordevices 230 that are capable of providing the same type of information,and may request the real-time information from a particular sensordevice 230 (e.g., may reduce an amount of redundant information that isreceived and/or processed, thereby conserving processor and/or memoryresources).

In some implementations, engagement platform 220 may determine a scorefor each sensor device 230, and request the real-time information fromsensor devices 230 that are associated with scores that satisfy athreshold, or the like. For example, engagement platform 220 maydetermine a score for a particular sensor device 230 based on an amountof user devices 210 that are providing the real-time information,associated with the particular sensor device 230, for display as an ARoverlay (e.g., may determine the score based on popularity, feedback,etc. associated with the particular sensor device 230).

In some implementations, engagement platform 220 may determine the setof sensor devices 230 based on performing a technique. For example,engagement platform 220 may use one or more machine learning techniquesto analyze data (e.g., training data) and create models. The techniquesmay include, for example, supervised and/or unsupervised techniques,such as artificial networks, case-based reasoning, Bayesian statistics,learning automata, Hidden Markov Modeling, linear classifiers, quadraticclassifiers, decision trees, association rule learning, or the like.Additionally, or alternatively, engagement platform 220 may use anotherkind of computer-implemented technique, such as artificial intelligence,machine perception, or computer vision, to analyze data and generatemodels.

In some implementations, engagement platform 220 may identify the set ofsensor devices 230 based on the geolocation information associated withuser device 210, and request the real-time information. In someimplementations, real-time information may include real-time sensorinformation which is output from sensor device 230 substantiallyconcurrently with sensor device 230 detecting the information.Additionally, or alternatively, real-time information may includeinformation which is provided, by user device 210 for display,substantially concurrently with sensor device 230 detecting theinformation (e.g., within a threshold time frame of sensor device 230detecting the information, providing the information to engagementplatform 220, or the like).

In some implementations, engagement platform 220 may provide, to sensordevices 230, requests that identify a time frame for which to providethe real-time information. Additionally, or alternatively, engagementplatform 220 may provide an instruction to sensor device 230 that causessensor device 230 to refrain from providing the real-time information(e.g., based on user device 210 not being associated with thegeolocation, not executing the AR application, or the like). In thisway, engagement platform 220 may request real-time information from asubset of sensor devices 230 that are associated with the geolocation,may request real-time information for a particular time frame, etc.,thereby conserving processor and/or memory resources of engagementplatform 220 and/or sensor devices 230, and/or thereby conservingnetwork resources.

As further shown in FIG. 4, process 400 may include receiving, from theset of sensor devices and/or a set of user devices, the real-timeinformation associated with the geolocation (block 430). For example,engagement platform 220 may receive, from the set of sensor devices 230and/or a set of user devices 210, real-time information associated withthe geolocation. In some implementations, sensor devices 230 may providereal-time information, such as live video information, environmentalcondition information, traffic information, parking information,security information, emergency information, etc. In someimplementations, engagement platform 220 may receive the real-timeinformation and perform a normalization technique, a standardizationtechnique, etc. For example, the set of sensor devices 230 may providedifferent types of information that include different data formats,different file types, etc. In this way, engagement platform 220 may moreefficiently process the information than as compared to if engagementplatform 220 does not perform the technique(s), thereby conservingprocessor and/or memory resources of engagement platform 220 and/or userdevice 210.

In some implementations, engagement platform 220 may analyze thereal-time information and detect a condition. For example, engagementplatform 220 may receive live video information from sensor devices 230,and perform an analytics technique to extract information such asparking availability, traffic conditions, pedestrian crowd levels, etc.In this way, engagement platform 220 may provide, to user devices 210,the real-time information and/or analytics information to enable usersof user devices 210 to identify particular conditions associated withthe geolocation. In some implementations, engagement platform 220 mayanalyze real-time information to identify a particular user, detect aparticular condition, or the like. That is, engagement platform 220 mayperform a surveillance technique in association with the real-timeinformation to detect a particular condition.

In some implementations, user devices 210 may provide, to engagementplatform 220, real-time information associated with the geolocation. Insome implementations, the real-time information associated with thegeolocation may include information that is provided, to engagementplatform 220, substantially concurrently with the occurrence of anunderlying event, activity, action, etc., with the capture of theinformation by user device 210 and/or sensor device 230, with thegeneration of the information by user device 210 and/or sensor device230, with the determination of the information by user device 210 and/orsensor device 230, or the like.

As an example, user devices 210 may provide information that identifiesuser generated content, such as reports indicating safety concerns,opinions regarding particular areas and/or proposed actions associatedwith the geolocation, requests for particular actions to be performed inassociation with the geolocation, conversations associated with thegeolocation, or the like.

As further shown in FIG. 4, process 400 may include providing, to theuser device, the real-time information associated with the geolocation(block 440). For example, engagement platform 220 may provide, to userdevice 210, the real-time information associated with the geolocation.In some implementations, engagement platform 220 may provide thereal-time information associated with the geolocation. Alternatively,engagement platform 220 may provide a subset of the real-timeinformation associated with the geolocation. For example, in a similarmanner as described above in connection with block 420, engagementplatform 220 may determine particular real-time information to provideto user device 210 based on a score associated with an underlying sensordevice 230 and/or user device 210, based on performing a technique,and/or the like.

In some implementations, engagement platform 220 may receive, from userdevice 210, information that identifies a particular sensor device 230for which engagement platform 220 is to provide the real-timeinformation. For example, a user of user device 210 may interact withuser device 210 to specify a particular sensor device 230 (e.g., atraffic camera associated with a particular intersection) for which toreceive the real-time information, and engagement platform 220 mayprovide the real-time information associated with the particular sensordevice 230. Additionally, or alternatively, a user of user device 210may specify a particular type of sensor device 230, and engagementplatform 220 may provide the real-time information associated with theparticular type of sensor device 230. In this way, engagement platform220 may provide real-time information associated with the geolocation,thereby reducing a need of the user to cause user device 210 to performsearches for particular types of information and conserving processor,memory, and/or network resources as a result.

As further shown in FIG. 4, process 400 may include receiving, from theserver device, the real-time information associated with the geolocation(block 450), and providing, for display via a user interface, thereal-time information associated with the geolocation as an augmentedreality overlay (block 460). For example, user device 210 may receive,from engagement platform 220, the real-time information associated withthe geolocation, and provide, for display via a user interface, thereal-time information including AR overlays.

In some implementations, user device 210 may provide multiple ARoverlays that correspond to different sensor devices 230. As an example,user device 210 may provide, for display, respective AR overlays thatcorrespond to real-time information associated with respective sensordevices 230. As an example, assume that a first AR overlay correspondsto a first area of the geolocation and that a second AR overlaycorresponds to a second area of the geolocation. In this case, the firstAR overlay may indicate that the first area is associated with a firstamount of people (e.g., a crowd), and the second AR overlay may indicatethat the second area is associated with a second amount of people thatis less than the first amount of people (e.g., is less crowded). Theuser may, for example, determine to take a particular action inassociation with the second area based on the real-time informationprovided as AR overlays.

In some implementations, a user may interact with user device 210 (e.g.,perform a touch gesture in association with an AR overlay) to select aparticular AR overlay. In this case, user device 210 may provide, fordisplay, the real-time information associated with sensor device 230. Insome implementations, the AR overlay may be indicative of the real-timeinformation. As an example, assume that a first sensor device 230 (e.g.,a sensor that may detect people) is associated with a first building,such as a store that is associated with a large crowd, or the like.Additionally, assume that a second sensor device 230 is associated witha second building that is associated with a smaller crowd as compared tothe first building. In this case, user device 210 may provide, fordisplay, a first AR overlay associated with the first sensor device 230that may be indicative of the large crowd (e.g., “busy,” “long wait timeexpected,” “crowded,” etc.). Additionally, the second AR overlay may beindicative of the smaller crowd associated with the second building(e.g., “quick wait times,” “immediate seating available,” etc.).

In some implementations, the AR overlay may include the real-timeinformation. For example, assume that an AR overlay corresponds to alive traffic feed of a particular intersection. In this case, the usermay interact with user device 210 to select the particular AR overlay,and user device 210 may provide, for display, real-time informationassociated with the live traffic feed (i.e., may display the livetraffic feed). In other implementations, the AR overlay may include livestreaming video content and/or streaming video content. For example,assume that sensor device 230 is capturing live video informationassociated with a geolocation. In this case, user device 210 mayprovide, for display, the live video information as an AR overlay.

In some implementations, engagement platform 220 may receive updatesregarding geolocation information of user device 210, and performoperations associated with blocks 420-440 based on the updatedgeolocation information. In some implementations, engagement platform220 may perform operations associated with blocks 420-440 based on acombination of information that identifies a geographic location of userdevice 210 and/or information that identifies an orientation of userdevice 210. For example, engagement platform 220 may perform operationsassociated with blocks 420-440 based on information that identifies ageographic location of user device 210 and information that identifiesan orientation of user device 210. Additionally, or alternatively,engagement platform 220 may perform operations associated with blocks420-440 based on information that identifies a geographic location ofuser device 210 or information that identifies an orientation of userdevice 210.

In some implementations, engagement platform 220 may perform operationsassociated with blocks 420-440 based on receiving information thatidentifies a geographic location (and/or an updated geographic location)of user device 210 (e.g., as a user moves in a particular directionwhile an orientation of user device 210 remains static). In other cases,engagement platform 220 may perform operations associated with blocks420-440 based on receiving information that identifies an orientation(and/or an updated orientation) of user device 210 (e.g., as anorientation of user device 210 changes while a geographic location ofuser device 210 remains static). Additionally, or alternatively, in yetother cases, engagement platform 220 may perform operations associatedwith blocks 420-440 based on receiving information that identifies ageographic location (and/or an updated geographic location) andinformation that identifies an orientation (and/or an updatedorientation) of user device 210.

In this way, implementations described herein enable engagement platform220 to determine a set of sensor devices 230 that are associated with aparticular geolocation, and provide, to user device 210, real-timeinformation associated with the set of sensor devices 230. In this way,a user of user device 210 may more readily identify informationassociated with a particular geolocation, which may reduce the need ofthe user to cause user device 210 to perform searches for particularinformation associated with the geolocation, thereby conservingprocessor and/or memory resources of user device 210.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIG. 5 is a flow chart of an example process 500 for providinginformation to an entity server based on crowdsourced informationassociated with a geolocation. In some implementations, one or moreprocess blocks of FIG. 5 may be performed by user device 210 and/orengagement platform 220. In some implementations, one or more processblocks of FIG. 5 may be performed by another device or a group ofdevices separate from or including user device 210 and/or engagementplatform 220 such as sensor device 230, entity server device 240,external server device 250, and/or kiosk device 260. In someimplementations, one or more process blocks of FIG. 5 may be performedbefore, after, concurrently with, in conjunction with, or based on oneor more process blocks of FIG. 4.

As shown in FIG. 5, process 500 may include providing, to a serverdevice, information that identifies user generated content associatedwith a geolocation (block 510). For example, user device 210 mayprovide, to engagement platform 220, information that identifies usergenerated content associated with a geolocation. In someimplementations, the user generated content may include an image, avideo, audio, text, etc., that may be indicative of an opinion regardingthe geolocation, an issue associated with the geolocation, a safetyconcern associated with the geolocation, an opinion regarding a proposedaction associated with the geolocation, a request for a particularaction to be performed in association with the geolocation, a request tosolicit feedback from other users associated with the geolocation, aninitiation of a conversation, an offer for sale of a good or service, arequest for a good or service, or the like.

For example, and in a similar manner as described above in connectionwith FIGS. 1A-1T, a user may interact with user device 210 to generateuser generated content. In some implementations, the user generatedcontent may be provided, for display by other user devices 210, as a“user pin.” In this way, engagement platform 220 may determine apriority level associated with particular user generated content, andmay provide, to user devices 210, information that identifies and/or isindicative of the priority level. Additionally, in this way, respectiveuser devices 210 may provide, for display, particular user generatedcontent based on the priority level, thereby facilitating discoursebetween users (e.g., citizens, entity officials, etc.) of thegeolocation.

As further shown in FIG. 5, process 500 may include receiving, from auser device, the information that identifies the user generated contentassociated with the geolocation (block 520), and receiving, from a setof other user devices and/or a set of sensor devices, responseinformation associated with the user generated content (block 530). Forexample, engagement platform 220 may receive, from user device 210, theinformation that identifies the user generated content, and may receive,from other user devices 210 and/or sensor devices 230, responseinformation associated with the user generated content and/or thegeolocation.

In some implementations, engagement platform 220 may receive, from userdevice 210, the information that identifies the user generated content,and provide the information that identifies the user generated contentto other user devices 210. For example, the other user devices 210 mayinclude AR applications, as discussed above in connection with FIGS.1A-1T, that enable the other user devices 210 to provide, for display,the information that identifies the user generated content. That is,other user devices 210 may provide, for display, information thatidentifies the user generated content based on geolocations of therespective user devices 210 coinciding with the geolocation of the usergenerated content. In some implementations, the other user devices 210may provide information that identifies the user generated content as ARoverlays.

In some implementations, engagement platform 220 may receive responseinformation based on providing the information that identifies the usergenerated content to the other user devices 210. In someimplementations, the response information may be indicative of anopinion regarding the user generated content (e.g., approval,disapproval, ambivalence, etc.), feedback regarding the user generatedcontent, corroboration of the user generated content, or the like. Forexample, users associated with the other user devices 210 may interactwith respective user devices 210 to provide response information (e.g.,an up-vote, a down-vote, a “like,” a flag, a comment, etc.) regardingthe user generated content.

In some implementations, sensor device 230 may provide, to engagementplatform 220, the response information. For example, sensor device 230may provide real-time information associated with a geolocation of theuser generated content. As an example, assume that user device 210provides information associated with user generated content thatidentifies a safety issue (e.g., “suspicious person spotted near thesubway station.”). In this case, engagement platform 220 may receive theinformation, and obtain response information from sensor devices 230associated with the geolocation of the user generated content. Forexample, engagement platform 220 may obtain camera imagery associatedwith the geolocation that corresponds to the time of generation of theuser generated content. In this way, engagement platform 220 mayprovide, to other user devices 210 and/or entity server device 240,information associated with the safety issue (e.g., an event), asdescribed elsewhere herein.

As further shown in FIG. 5, process 500 may include determining an eventbased on the information that identifies the user generated contentand/or the response information (block 540), and providing informationthat identifies the event (block 550). For example, engagement platform220 may determine an event based on the information that identifies theuser generated content and/or the response information, and provide, touser devices 210 and/or entity server device 240, information thatidentifies the event. In some implementations, engagement platform 220may process information associated with hundreds, thousands, millions,etc. of concurrent events. Additionally, engagement platform 220 may useone or more big data processing techniques to process the informationassociated with the events.

In some implementations, an event may be indicative of a safety issue, athreat, an environmental condition, a consensus regarding a request foran entity to perform a particular action, a consensus regarding arequest for an entity to refrain from taking a particular action, aconsensus regarding a particular proposal (e.g., a constructionproposal, a spend proposal, etc.) associated with a geolocation, anopinion regarding a particular geolocation, etc.

In some implementations, engagement platform 220 may determine an eventbased on the information that identifies the user generated content andthe response information. For example, engagement platform 220 mayidentify an amount of user devices 210 that have provided responseinformation, determine that the amount satisfies a threshold, anddetermine an event based on the amount satisfying the threshold.Additionally, or alternatively, engagement platform 220 may determine anevent based on performing a sentiment analysis, performing analytics inassociation with the user generated content and/or the responseinformation, determining a nature of the response information (e.g., anamount of user devices 210 that have provided positive feedback, such asan up-vote), or the like.

In some implementations, engagement platform 220 may determine an eventbased on an amount of user devices 210 that are associated with similaruser generated content. For example, assume that a set of user devices210 provide, to engagement platform 220, information that identifiessimilar user generated content (e.g., content involving the same issue,content involving the same request, etc.). In this case, engagementplatform 220 may determine an event based on an amount of user devices210 that provided the similar user generated content.

In some implementations, engagement platform 220 may determine an eventbased on activities associated with respective user devices 210. Forexample, assume that user devices 210 are executing an AR application.In this case, engagement platform 220 may collect information associatedwith user devices 210 that are executing the AR application (e.g.,application activity), and determine an event based on the information.As examples, engagement platform 220 may identify that a thresholdamount of user devices 210 are associated with a particular mission, arelocated in a particular geolocation, have completed a particularmission, are performing a particular mission, have provided feedbackregarding a particular mission, or the like. In this way, a userassociated with entity server device 240 may identify analyticsassociated with a particular geolocation and determine an amount ofparticular activity associated with an AR application regarding thegeolocation. In this way, engagement platform 220 may receiveinformation associated with user devices 210, without requiring thatusers of user devices 210 interact with user devices 210 to generatecontent. That is, engagement platform 220 may receive analyticsinformation associated with user devices 210 and/or sensor devices 230.

In some implementations, engagement platform 220 may provide, to entityserver device 240, information that identifies the event. For example,entity server device 240 may provide, to a user device 210 associatedwith the entity, information associated with a dashboard (e.g., a userinterface). Additionally, a user (e.g., an official associated with theentity, or the like) may view, via the dashboard, the information thatidentifies the event. For example, user device 210 (e.g., associatedwith the entity) may provide, for display via the dashboard, informationthat identifies the user generated content and response information fromother user devices 210 and/or sensor devices 230.

In some implementations, a user associated with the entity may interactwith a respective user device 210, which may cause information to beprovided to engagement platform 220 and/or other user devices 210.Continuing the example described elsewhere herein, assume that the userassociated with the entity views the user generated content (e.g.,“suspicious person spotted near the subway station”), and identifies,based on imagery received from sensor devices 230, a potential suspect.In this case, the user associated with the entity may interact with therespective user device 210 to generate alert information (e.g., “Armedsuspect in the area. Take shelter.”). Additionally, the respective userdevice 210 may cause entity server device 240 to provide, to engagementplatform 220 and/or user devices 210, the alert information and/orinformation associated with imagery captured from sensor devices 230(e.g., an image of the potential suspect). In this way, user devices210, that are located within, nearby, etc. the geolocation, may receivethe alert information and may provide, for display, the alertinformation (e.g., as an AR overlay).

In some implementations, engagement platform 220 may automaticallypermit and/or cause an action to be performed based on the usergenerated content and/or the response information. Continuing with theabove example, engagement platform 220 may automatically notify devicesassociated with emergency vehicles and/or emergency personnel (e.g., apolice department, a fire department, etc.) to provide assistance inassociation with the geolocation, or the like. Additionally, oralternatively, engagement platform 220 may provide, to user devices 210,the alert information without requiring that a user of the entity causeengagement platform 220 to provide the alert information.

In this way, implementations described herein enable user device 210 toprovide, to engagement platform 220, information that identifies usergenerated content. Additionally, implementations described herein enableengagement platform 220 may receive response information, and determinean event based on the information that identifies the user generatedcontent and/or the response information. Engagement platform 220 mayprovide, to entity server device 240, information that identifies theevent, thereby enabling an entity to determine particular informationassociated with the geolocation and take appropriate action. In thisway, implementations described herein conserve processor and/or memoryresources by aggregating similar information and providing theinformation to entity server device 240, thereby reducing a need ofmanual processing of various information to identify events, eliminatingsubjective analysis of the various information, etc.

Additionally, implementations described herein enable users associatedwith a geolocation (e.g., citizens, inhabitants, visitors, governmentofficials, agency officials, etc.) to exchange information in a seamlessand transparent manner, thereby increasing trust and transparencybetween users of the geolocation.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5. Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

FIGS. 6A-6E are diagrams of an example implementation 600 relating toexample process 500 shown in FIG. 5. FIGS. 6A-6E show an example ofproviding information to an entity server based on crowdsourcedinformation associated with a geolocation.

As shown in FIG. 6A, and by reference number 605, engagement platform220 may receive, from user device 210-A, information associated withuser generated content. For example, as shown, a user of user device210-A may interact with user device 210-A to cause user device 210-A togenerate user generated content (e.g., text indicating “There should bea traffic light at this intersection!”), and provide, to engagementplatform 220, information that identifies the user generated content. Asshown by reference number 610, engagement platform 220 may provide, touser devices 210-B, C, and D, information that identifies the usergenerated content as an AR overlay on user devices 210-B, C, and D(e.g., based on user devices 210-B, C, and D being located within athreshold distance of the geolocation associated with the user generatedcontent). As an example, assume that users, associated with user devices210-B, C, and D interact with respective user devices 210 (e.g., toprovide feedback, such as an up-vote associated with the user generatedcontent).

As shown in FIG. 6B, and by reference number 615, engagement platform220 may receive, from user devices 210-B, C, and D, response informationassociated with the user generated content. As shown by reference number620, engagement platform 220 may determine an event indicating that anamount of user devices 210 that have provided response informationsatisfies a threshold. In this case, and as shown by reference number625, engagement platform 220 may provide, to entity server device 240,information that identifies the event.

As shown in FIG. 6C, and as shown by reference number 630, entity serverdevice 240 may provide, to user device 210-E, information thatidentifies the event. As shown, user device 210-E may provide, fordisplay, information that identifies the event, information thatidentifies the user generated content, and/or response information. Inthis way, a user (e.g., a city official) of user device 210-E may viewthe particular information associated with the geolocation. For example,assume that the user of user device 210-E determines that theintersection associated with the user generated content poses a riskwithout the proposed traffic light. In this case, the user of userdevice 210-E may interact with user device 210-E to generate alertinformation (e.g., “A traffic light will be implemented soon. Exercisecaution in the interim.”).

As shown in FIG. 6D, and by reference number 635, engagement platform220 may receive, from entity server device 240, alert informationassociated with the user generated content. As shown by reference number640, engagement platform 220 may provide, to user devices 210-F and210-G, the alert information. For example, assume that user devices210-F and 210-G are located within a threshold distance of thegeolocation of the user generated content (e.g., are nearby theintersection).

As shown in FIG. 6E, user device 210-G may provide, for display, thealert information as an AR overlay. For example, as shown, user device210-G may provide, for display, imagery associated with the geolocationand may provide the alert information as a superimposed AR overlay. Inthis way, user device 210-G may provide, for display, information thatis pertinent to a geolocation of user device 210-G (e.g., as determinedby users of other user devices 210 and/or a user associated with entityserver device 240).

As indicated above, FIGS. 6A-6E are provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIGS. 6A-6E.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold may refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, etc.

Certain user interfaces have been described herein and/or shown in thefigures. A user interface may include a graphical user interface, anon-graphical user interface, a text-based user interface, etc. A userinterface may provide information for display. In some implementations,a user may interact with the information, such as by providing input viaan input component of a device that provides the user interface fordisplay. In some implementations, a user interface may be configurableby a device and/or a user (e.g., a user may change the size of the userinterface, information provided via the user interface, a position ofinformation provided via the user interface, etc.). Additionally, oralternatively, a user interface may be pre-configured to a standardconfiguration, a specific configuration based on a type of device onwhich the user interface is displayed, and/or a set of configurationsbased on capabilities and/or specifications associated with a device onwhich the user interface is displayed.

To the extent the aforementioned embodiments collect, store, or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Additionally, thecollection, storage, and use of such information may be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as may be appropriate for thesituation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A device, comprising: one or more processors to:receive, from a user device, information that identifies a geolocationof the user device; determine a set of sensor devices that areassociated with the geolocation; request, from the set of sensordevices, real-time information associated with the geolocation based ondetermining the set of sensor devices; receive, from the set of sensordevices, the real-time information associated with the geolocation basedon requesting the real-time information; and provide, to the userdevice, the real-time information associated with the geolocation topermit the user device to provide, for display via a user interface, thereal-time information as an augmented reality overlay.
 2. The device ofclaim 1, where the one or more processors are further to: receive, fromthe user device, information that identifies user generated content;provide, to a set of other user devices, the information that identifiesthe user generated content; receive, from the set of other user devices,response information based on providing the information that identifiesthe user generated content; determine an event based on the informationthat identifies the user generated content and the response information;and provide, to another device, information that identifies the event,the other device being associated with an entity to perform a particularaction in association with the geolocation based on the information thatidentifies the event.
 3. The device of claim 1, where the one or moreprocessors are further to: receive, from the user device, informationthat identifies a sensor device, of the set of sensor devices, for whichto receive the real-time information associated with the geolocation;and where the one or more processors, when requesting the real-timeinformation associated with the geolocation, are to: request thereal-time information based on the information that identifies thesensor device.
 4. The device of claim 1, where the one or moreprocessors are further to: receive, from another device, informationthat identifies an event associated with the geolocation, the otherdevice being associated with an entity that is associated with thegeolocation; and provide, to the user device, the information thatidentifies the event to permit the user device to provide, for display,the information that identifies the event as another augmented realityoverlay.
 5. The device of claim 1, where the one or more processors arefurther to: receive, from another device, information that identifies anevent associated with the geolocation; receive, from a sensor device ofthe set of sensor devices, information associated with the event; andprovide, to the user device, the information that identifies the eventassociated with the geolocation and the information associated with theevent.
 6. The device of claim 1, where the one or more processors arefurther to: receive, from another user device, information thatidentifies user generated content associated with the geolocation; andprovide, to the user device, the information that identifies the usergenerated content to permit the user device to provide, for display, theinformation that identifies the user generated content as anotheraugmented reality overlay.
 7. The device of claim 1, where the one ormore processors are further to: receive information that identifies ageographic location of the user device; receive information thatidentifies an orientation of the user device; and where the one or moreprocessors, when determining the set of sensor devices, are to:determine the set of sensor devices based on the information thatidentifies the geographic location of the user device and theinformation that identifies the orientation of the user device.
 8. Anon-transitory computer-readable medium storing instructions, theinstructions comprising: one or more instructions that, when executed byone or more processors, cause the one or more processors to: receive,from a user device, information that identifies a geolocation of theuser device; request, from a set of sensor devices that are associatedwith the geolocation, real-time information associated with thegeolocation based on the information that identifies the geolocation;receive, from the set of sensor devices, the real-time informationassociated with the geolocation; and provide, to the user device, thereal-time information associated with the geolocation to permit the userdevice to provide, for display, the real-time information as anaugmented reality overlay.
 9. The non-transitory computer-readablemedium of claim 8, where the one or more instructions, when executed bythe one or more processors, further cause the one or more processors to:receive, from the user device, information that identifies usergenerated content associated with the geolocation; and provide, toanother device, the information that identifies the user generatedcontent, the other device being associated with a government entityassociated with the geolocation.
 10. The non-transitorycomputer-readable medium of claim 8, where the one or more instructions,when executed by the one or more processors, further cause the one ormore processors to: receive, from another device, information thatidentifies an alert associated with the geolocation, the other devicebeing associated with a government agency; and provide, to the userdevice, the information that identifies the alert to permit the userdevice to provide, for display, the information that identifies thealert as another augmented reality overlay.
 11. The non-transitorycomputer-readable medium of claim 8, where the one or more instructions,when executed by the one or more processors, further cause the one ormore processors to: receive, from another device, information thatidentifies an event associated with the geolocation; receive, from asensor device of the set of sensor devices, information associated withthe event; and provide, to the user device, the information thatidentifies the event associated with the geolocation and the informationassociated with the event.
 12. The non-transitory computer-readablemedium of claim 8, where the one or more instructions, when executed bythe one or more processors, further cause the one or more processors to:receive, from another user device, information that identifies usergenerated content associated with the geolocation; and provide, to theuser device, the information that identifies the user generated contentto permit the user device to provide, for display, the information thatidentifies the user generated content as another augmented realityoverlay.
 13. The non-transitory computer-readable medium of claim 8,where the one or more instructions, when executed by the one or moreprocessors, further cause the one or more processors to: determine theset of sensor devices based on scores associated with the set of sensordevices; and where the one or more instructions, that cause the one ormore processors to request the real-time information, cause the one ormore processors to: request the real-time information based on thescores associated with the set of sensor devices.
 14. The non-transitorycomputer-readable medium of claim 8, where the one or more instructions,when executed by the one or more processors, further cause the one ormore processors to: receive, from the user device, information thatidentifies a type of sensor device; and where the one or moreinstructions, that cause the one or more processors to request thereal-time information, cause the one or more processors to: request thereal-time information based on the type of sensor device.
 15. A method,comprising: receiving, by a device and from a user device, informationthat identifies a geolocation and an orientation of the user device;determining, by the device, a set of sensor devices that are associatedwith the geolocation and the orientation; requesting, by the device andfrom the set of sensor devices, real-time information associated withthe geolocation; receiving, by the device and from the set of sensordevices, the real-time information associated with the geolocation; andproviding, by the device and to the user device, the real-timeinformation associated with the geolocation to permit the user device toprovide, for display, the real-time information as an augmented realityoverlay.
 16. The method of claim 15, further comprising: receiving, fromthe user device, information that identifies user generated contentassociated with the geolocation; receiving, from a set of other userdevices, information that identifies other user generated contentassociated with the geolocation; determining an event based on theinformation that identifies the user generated content and theinformation that identifies the other user generated content; andproviding, to another device, information that identifies the event. 17.The method of claim 15, further comprising: receiving, from anotherdevice, information that identifies an event associated with thegeolocation, the other device being associated with an organizationassociated with the geolocation; and providing, to the user device, theinformation that identifies the event to permit the user device toprovide, for display, the information that identifies the event asanother augmented reality overlay.
 18. The method of claim 15, furthercomprising: receiving, from another device, information that identifiesan event; receiving, from a sensor device of the set of sensor devices,information associated with the event; and providing, to the userdevice, the information associated with the event to permit the userdevice to provide, for display, the information associated with theevent as another augmented reality overlay.
 19. The method of claim 15,further comprising: receiving, from another user device, informationthat identifies user generated content associated with the geolocation;and providing, to the user device, the information that identifies theuser generated content to permit the user device to provide, fordisplay, the information that identifies the user generated content asanother augmented reality overlay.
 20. The method of claim 15, furthercomprising: receiving, from a set of user devices, informationassociated with the geolocation, the set of user devices including theuser device; determining that an amount of user devices, of the set ofuser devices, satisfies a threshold; and providing, to another device,the information associated with the geolocation, the other device beingassociated with a government entity that is associated with thegeolocation.